Non-Functional Requirements for Object-Oriented Modeling
نویسندگان
چکیده
Recently, it has been pointed out that the majority of the requirements engineering methods do not take into account non-functional requirements (NFRs) [10][11]. Consequently, we have been experiencing serious problems during the development of software systems, such as cost and schedule overruns. In order to diminish this negligence of NFRs and its consequences, this work proposes a strategy (OONFR) that brings NFRs to object-oriented modeling. The OONFR strategy uses as input a Language Extended Lexicon of the Universe of Discourse (LEL of UofD) and outputs a class diagram with indications of what classes, attributes, operations and relationships are responsible for satisficing NFRs. This strategy consists of the following activities: build the Language Extended Lexicon of Universe of Discourse-NFR (LEL of UofD-NFR), build the scenarios and build the class diagram.
منابع مشابه
Domain-driven Architecture for Object-oriented Software System
The Unified Modeling Language (UML) is one of the important modeling languages used to design the software problems. The main aim of this paper is to develop a complete process of software architecture for the object-oriented software system. This software architecture will ensure non-functional requirements as well as the functional requirements of the software system. The software architectur...
متن کاملREquirements, Aspects and Software Quality: the REASQ model
Object-oriented analysis and design have been more concerned with system functionality, neglecting non-functional aspects; the result is code which is tangled and difficult to maintain, contradicting main principles of object orientation. Aspect Oriented Software Development (AOSD) proposes the early specification of non-functional requirements. However, a standard and homogenous vision of the ...
متن کاملReflection and Object-Oriented Analysis
Traditional methods for object-oriented analysis and modeling focus on the functional specification of software systems. Nonfunctional requirements such as fault-tolerance, distribution, integration with legacy systems, and the like, do not have a clear collocation within the analysis process, as they are related to the architecture and workings of the system itself rather than the application ...
متن کاملModelsaz: An Object-Oriented Computer-Aided Modeling Environment
Modeling and simulation of processing plants are widely used in industry. Construction of a mathematical model for a plant is a time-consuming and error-prone task. In light of extensive advancements in computer science (both hardware and software), computers are becoming a necessary instrument in industrial activities. Many software tools for modeling, simulation and optimization of proces...
متن کاملReviewing Testability of Object Oriented Systems for Non - Functional Specifications
The object oriented programming proves to be the most beneficial paradigm for scalable and maintainable software development. An object characterizes special features like encapsulation, inheritance, modularity and polymorphism. The processes in Test Driven Design closely relate the agile methodology and strengthen the need of testing during the development stages. The UML specifies the archite...
متن کاملAn Approach to Specifying Concurrent, Distributed, and Autonomous Object Behaviors Using a High-Level Meta-Object Protocol
To develop distributed applications requires to consider not only functional requirements but also nonfunctional requirements such as distributions, synchronizations, and scheduling policies. Specifying such non-functional requirements is necessary for supporting on-line capabilities of Autonomous Decentralized Systems (ADS). However, the existing design notations and methods do not address suc...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2000